|
|
| Author |
Thread Statistics | Show CCP posts - 62 post(s) |
|
CCP Explorer
C C P
C C P Alliance
526
   |
Posted - 2012.06.04 19:56:00 -
[1] - Quote
I wanted to expand a bit on CCP Soundwave's comment in his dev blog that "doing frequent updates isnGÇÖt really healthy and canGÇÖt be maintained for longer periods of time" from a technical perspective. In this particular case then the frequent Inferno 1.0.x releases are starting to press against the staging process of the next main deployment.
Let me explain a bit what I mean by that:
We use a source code revision control system to manage the source code for EVE Online (we use a system called Perforce). We develop each expansion in a code branch called MAIN but shortly before deployment we copy the code (port it) into a different branch for the final fixes; isolating the code being deployed so that future development can continue uninterrupted in MAIN for the future deployments thereafter.
After a deployment we hotfix the server and deploy client patches from the staging branch until the subsequent staging branch is created. The reason why we only have one staging branch active at each time is that code fixes made in a old staging branch can't be ported directly to the new staging branch, but rather must be ported through the MAIN branch, potentially picking up extra/new code in the process that is intended for a later release.
In this diagram you can see the staging branches for Inferno 1.0.x (called DEBBY) and the upcoming Inferno 1.1.x (called ERNESTO):
http://cdn1.eveonline.com/www/newssystem/media/62833/1/Branches_H2_2012_v6a_small.png
We were planning to stage Inferno 1.1.x on 6 June but have pushed that back to 7 June to give the team working on the Unified Inventory all the time possible for updates of Inferno 1.0.x, before we must create the staging branch for Inferno 1.1.x to allow the teams working on that release to finalise their deployment. There are then going to be more updates to Unified Inventory in Inferno 1.1.x as CCP Soundwave detailed in the dev blog.
Erlendur S. Thorsteinsson | Software Director | EVE Online, CCP Games | Follow on: Twitter / Google+ |
|
|
CCP Explorer
C C P
C C P Alliance
529
|
Posted - 2012.06.04 21:28:00 -
[2] - Quote
Panhead4411 wrote:CCP Explorer wrote:I wanted to expand a bit on CCP Soundwave's comment in his dev blog that "doing frequent updates isnGÇÖt really healthy and canGÇÖt be maintained for longer periods of time" from a technical perspective. In this particular case then the frequent Inferno 1.0.x releases are starting to press against the staging process of the next main deployment.
We were planning to stage Inferno 1.1.x on 6 June but have pushed that back to 7 June to give the team working on the Unified Inventory all the time possible for updates of Inferno 1.0.x, before we must create the staging branch for Inferno 1.1.x to allow the teams working on that release to finalise their deployment. There are then going to be more updates to Unified Inventory in Inferno 1.1.x as CCP Soundwave detailed in the dev blog. So is this the real reason the new Inventory was initially PUSHED onto TQ? I understand and appreciate that you have in house dealines, but you seem to not be understanding that your customers would prefer a fully functional system before you try to work on something new. Unless i've misread most of the feedback given in all the major threadnaughts thus far. This is not the reason. We honestly thought we were ready.
Erlendur S. Thorsteinsson | Software Director | EVE Online, CCP Games | Follow on: Twitter / Google+ |
|
|
CCP Explorer
C C P
C C P Alliance
529
|
Posted - 2012.06.04 21:29:00 -
[3] - Quote
Sarmatiko wrote:CCP Explorer wrote:In this diagram you can see the staging branches for Inferno 1.0.x (called DEBBY) and the upcoming Inferno 1.1.x (called ERNESTO): http://cdn1.eveonline.com/www/newssystem/media/62833/1/Branches_H2_2012_v6a_small.pngWe were planning to stage Inferno 1.1.x on 6 June but have pushed that back to 7 June to give the team working on the Unified Inventory all the time possible for updates of Inferno 1.0.x, before we must create the staging branch for Inferno 1.1.x to allow the teams working on that release to finalise their deployment. There are then going to be more updates to Unified Inventory in Inferno 1.1.x as CCP Soundwave detailed in the dev blog. Thanks for great explanation. So we will probably get minmatar ships in ERNESTO branch in June?  Yes, you will.
Erlendur S. Thorsteinsson | Software Director | EVE Online, CCP Games | Follow on: Twitter / Google+ |
|
|
CCP Explorer
C C P
C C P Alliance
529
|
Posted - 2012.06.04 21:33:00 -
[4] - Quote
Fearless M0F0 wrote:CCP Explorer wrote:We use a source code revision control system to manage the source code for EVE Online (we use a system called Perforce). Perforce?, ouch, I feel your pain  You guys should look into some 21st century source control like Git or Mercurial, each team working on its own branch until is ready to merge into the mainline. While Perforce has many shortcomings it excels at large-file management. Other systems have better change-set management but can't cope with our art assets.
Erlendur S. Thorsteinsson | Software Director | EVE Online, CCP Games | Follow on: Twitter / Google+ |
|
|
CCP Explorer
C C P
C C P Alliance
543
|
Posted - 2012.06.06 14:55:00 -
[5] - Quote
MailDeadDrop wrote:CCP Explorer wrote:We were planning to stage Inferno 1.1.x on 6 June but have pushed that back to 7 June Uh, less than 24 hours before deployment, and there's still no patch notes. Someone forget to follow procedure again? http://community.eveonline.com/updates/patchnotes.asp We are staging it and updating Singularity. Deployment to Tranquility is scheduled 19 June.
Erlendur S. Thorsteinsson | Software Director | EVE Online, CCP Games | Follow on: Twitter / Google+ |
|
|
CCP Explorer
C C P
C C P Alliance
543
|
Posted - 2012.06.06 16:49:00 -
[6] - Quote
MailDeadDrop wrote:CCP Explorer wrote:MailDeadDrop wrote:CCP Explorer wrote:We were planning to stage Inferno 1.1.x on 6 June but have pushed that back to 7 June Uh, less than 24 hours before deployment, and there's still no patch notes. Someone forget to follow procedure again? http://community.eveonline.com/updates/patchnotes.asp We are staging it and updating Singularity. Deployment to Tranquility is scheduled 19 June. Oh, sorry. Perhaps that was my misunderstanding. Soundwave's dev blog said: "Those improvements are going out Thursday, June 7" and I read Explorer's note (above) incorrectly as being about that (it isn't; Explorer was referring to the date that the bigger Inferno 1.1.x release was going to Sisi). So, is there a release hitting Tranquility on the 7th? (Just to clarify, Explorer, I don't expect patch notes for Sisi deployments before the Sisi deployment. There is such a thing as too much. I expect preliminary patch notes for stuff on Sisi after you're ready for us to beat on Sisi, and final patch notes for stuff going to Tranquility before release to Tranquility.) Sorry for the confusion; yes, there are deployments on 7 June (tomorrow) and then on 19 June. It's Inferno 1.0.9 and then Inferno 1.1. Both deployments will contain fixes to Unified Inventory. Inferno 1.1 primarily contains updated Minmatar ships (continuing the so-called V3 Project).
After 19 June there will further releases, Inferno 1.1.x, as needed and as promised, for Unified Inventory.
Erlendur S. Thorsteinsson | Software Director | EVE Online, CCP Games | Follow on: Twitter / Google+ |
|
|
CCP Explorer
C C P
C C P Alliance
544
|
Posted - 2012.06.06 19:01:00 -
[7] - Quote
MailDeadDrop wrote:CCP Explorer wrote:Sorry for the confusion; yes, there are deployments on 7 June (tomorrow) and then on 19 June. It's Inferno 1.0.9 and then Inferno 1.1. Both deployments will contain fixes to Unified Inventory. Inferno 1.1 primarily contains updated Minmatar ships (continuing the so-called V3 Project).
After 19 June there will further releases, Inferno 1.1.x, as needed and as promised, for Unified Inventory. Ok; thanks for the clarification. So I renew my earlier request: where are the patch notes for Inferno 1.0.9? I would think that they would be available at least 24 hours prior to deployment. The build is made at 04:00 GMT and the patch notes are collected in the morning. This is the process we have for the point patches (the 1.0.x patches).
Erlendur S. Thorsteinsson | Software Director | EVE Online, CCP Games | Follow on: Twitter / Google+ |
|
|
CCP Explorer
C C P
C C P Alliance
544
|
Posted - 2012.06.06 19:01:00 -
[8] - Quote
Sarmatiko wrote:CCP Mannbj+¦rn wrote:It is good hear that there is interest in the V3 project. I'm sorry to say that there are no plans to make a Minmatar DEV blog right now that I know off but that might change now that we are getting closer to delivery. Well dev blog about new .black format instead of .red should be kinda interesting. There must be reasons why this new format was implemented - maybe it's for client performance optimization brought by Team Gridlock, or maybe this is first step to ship customization (like user modified RGB values for ship material/masks/lights). We don't know this, but you do!  I'll talk to Team Gridlock.
Erlendur S. Thorsteinsson | Software Director | EVE Online, CCP Games | Follow on: Twitter / Google+ |
|
|
CCP Explorer
C C P
C C P Alliance
554
|
Posted - 2012.06.08 20:38:00 -
[9] - Quote
CCP Goliath wrote:It wasn't an admission, we have a massive number of legacy builds because we need to test against previous functionality. It's also not a case of us not believing people, it would be naive to assume that people are actively lying to us about a system. We can't open our reference servers to the public however as they have sensitive data on them (all internal mirrors are unpruned and remirroring for a reference server would cause a bunch of conflicts). It's also not quite as simple as just whacking a VM based server up and letting that be public, you're just going to have to take my word for that. The reference servers are set up to support perhaps 5-10 users; only for internal testing purposes.
Erlendur S. Thorsteinsson | Software Director | EVE Online, CCP Games | Follow on: Twitter / Google+ |
|
|
|
| |
|